From 5a3fe9e5f5dc9a4acc36d6a5bbec20c7db3b6a0b Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Sun, 24 May 2020 11:07:45 -0400 Subject: [PATCH] docs: Convert resources section to markdown --- docs/reference/gtk/meson.build | 4 +- .../gtk/{resources.xml => resources.md} | 55 +++---------------- 2 files changed, 11 insertions(+), 48 deletions(-) rename docs/reference/gtk/{resources.xml => resources.md} (52%) diff --git a/docs/reference/gtk/meson.build b/docs/reference/gtk/meson.build index 9f7ac480d4..6c2170a115 100644 --- a/docs/reference/gtk/meson.build +++ b/docs/reference/gtk/meson.build @@ -353,7 +353,6 @@ content_files = [ 'gtk4-widget-factory.xml', 'overview.xml', 'question_index.xml', - 'resources.xml', 'text_widget.xml', 'tree_widget.xml', 'visual_index.xml', @@ -371,8 +370,9 @@ expand_content_md_files = [ 'osx.md', 'wayland.md', 'windows.md', - 'x11.md', +: 'x11.md', 'getting_started.md', + 'resources.md', 'building.md', 'compiling.md', 'running.md', diff --git a/docs/reference/gtk/resources.xml b/docs/reference/gtk/resources.md similarity index 52% rename from docs/reference/gtk/resources.xml rename to docs/reference/gtk/resources.md index 1743708e2e..c2cc2d36a5 100644 --- a/docs/reference/gtk/resources.xml +++ b/docs/reference/gtk/resources.md @@ -1,76 +1,39 @@ - - - - -Contact information and bug reports -3 -Contact information and bug reports - +# Contact information and bug reports {#gtk-resources} - -Contact information and bug reports - -Getting help with GTK - - +## Opening a bug or feature request - -Opening a bug or feature request - - If you encounter a bug, misfeature, or missing feature in GTK, please -file a bug report on our -GitLab project. +file a bug report on our [GitLab project](https://gitlab.gnome.org/GNOME/gtk/issues/new). You should also file issues if the documentation is out of date with the existing API, or unclear. - - Don't hesitate to file a bug report, even if you think we may know about it already, or aren't sure of the details. Just give us as much information as you have, and if it's already fixed or has already been discussed, we'll add a note to that effect in the report. - - The issue tracker should definitely be used for feature requests, it's not only for bugs. We track all GTK development in GitLab, to ensure that nothing gets lost. - - - - -Working on GTK +## Working on GTK - If you develop a bugfix or enhancement for GTK, please open a merge request in GitLab as well. You should not attach patches to an issue, or describe the fix as a comment. Merge requests allow us to build GTK with your code applied, and run the test suite, on multiple platforms and architectures, and verify that nothing breaks. They also allow us to do proper code reviews, so we can iterate over the changes. - - -You should follow the contribution guide +You should follow the [contribution guide](https://gitlab.gnome.org/GNOME/gtk/blob/master/CONTRIBUTING.md) for GTK, available on GitLab. - - If you want to discuss your approach before or after working on it, good ways to contact the GTK developers, apart from GitLab issues, are - -the #gtk IRC channel on irc.gnome.org -the gtk tag on the GNOME Discourse instance - -You should not send patches by email, as they will inevitably get lost, -or forgotten. Always open a merge request. - - +- the #gtk IRC channel on irc.gnome.org +- the gtk tag on the <[GNOME Discourse instance](https://discourse.gnome.org/tag/gtk) - +You should not send patches by email, as they will inevitably get lost, +or forgotten. Always open a merge request. -- 2.30.2